…8598)

## Problem

When users click “Open in VS Code” from the Lambda console and the
request reaches Toolkit without an active connection or with mismatched
credentials, Toolkit currently falls back to console credential login
(`aws login`) immediately. This triggers a browser-based authentication
flow without prior notice.



## Solution

This change adds a modal confirmation dialog before invoking `aws login`
in these cases. The dialog explains that Toolkit will sign in using
browser-based authentication and states the required prerequisites.
Users must explicitly choose to continue before the console login flow
starts.



The prompt:
- Explains that signing in is required to open the Lambda function
locally
- Informs users that browser-based authentication will occur
- States the AWS CLI and permission prerequisites
- Allows users to explicitly choose whether to proceed

This makes the flow intentional, reduces surprise browser redirects, and
helps distinguish between informed cancellation and setup issues.

## Screenshots



<img width="1197" height="800" alt="Screenshot 2026-02-23 at 3 53 57 PM"
src="https://github.com/user-attachments/assets/8e7d0c64-7506-4e13-8ec5-322ca720003f"
/>


---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

… prompt a warning (#8610)

## Problem

The SMUS agent context prompt was displayed as an information
notification that users were easily overlooking or ignoring.
Additionally, there was no telemetry to track how users responded to the
prompt (accepted, declined, or dismissed), making it impossible to
measure engagement.

## Solution

Changed the prompt from showInformationMessage to showWarningMessage for
higher visibility. Added telemetry using smus_acceptAgentsNotification
to track whether users accept, decline, or dismiss the prompt.
---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

Co-authored-by: Ziwei Ba <ziwikiwi@amazon.com>

… for MCP servers (#8608)

## Problem
Kiro struggles to troubleshoot credential issues when MCP server doesn't
have the proper credentials environment variable, even though it's
mentioned in the smus-context file.


## Solution
Add a prompt to smus-context.md to include credentials provider uri in
MCP server env block.

---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

Co-authored-by: kzr-at-amazon <build@amazon.com>

… user choice (#8611)

## Problem
Previously, we emitted a metric when a user chooses Yes, No, or closes
out of the prompt. However, sometimes the notification is buried or goes
to the little notification bell. We also want to see if users will
actually see the prompt.

## Solution

- Changed existing agent context metric to two metrics:
  - smus_agentContextShowPrompt — emitted when the prompt is displayed
- smus_agentContextUserChoice — emitted when the user accepts, declines,
or dismisses the prompt
- Both metrics include rich context: domain ID, account ID, region,
project ID, project account ID, project region, space key, and auth
mode.

---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: Ziwei Ba <ziwikiwi@amazon.com>

…#8620)

## Problem
The `sagemaker-ssh-kiro` extension VSIX is showing up in the release
artifacts for prerelease, but we don't want it to show there. It's
intended only to be embedded inside of the toolkit VSIX.

## Solution
Remove the `sagemaker-ssh-kiro` extension VSIX from the top level file
system during the GitHub Action workflow step which packages the VSIX
files.

---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

## Problem
Did not include "Result: Success" in the emitted metric for showing the
AGENTS.md prompt, which resulted in a warning when logging the metric.

## Solution
Added this missing field.

---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

Co-authored-by: Ziwei Ba <ziwikiwi@amazon.com>
Co-authored-by: Will Lo <96078566+Will-ShaoHua@users.noreply.github.com>

…state (#8599)

## Problem


## Solution
simply revert to whatever document initial content is

---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

## Problem


## Solution


---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: aws-toolkit-automation <>
Co-authored-by: Laxman Reddy <141967714+laileni-aws@users.noreply.github.com>

)

## Problem


## Solution


---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

Co-authored-by: invictus <149003065+ashishrp-aws@users.noreply.github.com>